.pre-commit-config.yaml (1)

1-23: ⚡ Quick win

Consider merge-commit handling (and verify linter CLI flag support).

With conventional-precommit-linter running at commit-msg and no merge-skip/exception config, local merges may be rejected due to default merge messages (e.g., Merge branch ... into ...). You already document git commit --no-verify in CONTRIBUTING.md, but it may not apply cleanly to all commit-creating commands (merge/cherry-pick/rebase), and the linter may also have a “skip merge commits” option.

Please verify:

1. Whether this linter supports an option to skip merge commits (or treat them as exempt), and
2. That the provided --types=..., --subject-min-length, --subject-max-length, and --allow-breaking flags match the linter’s expected CLI syntax for v1.11.0.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.pre-commit-config.yaml around lines 1 - 23, The commit-msg hook
configuration for the conventional-precommit-linter (hook id:
conventional-precommit-linter) may reject merge commits and/or be using
incorrect CLI flags; verify whether v1.11.0 supports a "skip merge commits" or
equivalent flag (or an allow/ignore pattern) and confirm the exact flag
names/syntax for --types, --subject-min-length, --subject-max-length and
--allow-breaking; if the linter supports skipping merges, update the hook args
to include that flag (or add an explicit exempt pattern for merge commit
messages), otherwise adjust the configuration to a supported flag syntax or add
documentation instructing use of --no-verify for automated merges and rebases so
that merge/cherry-pick/rebase workflows aren’t blocked (refer to the hook id
conventional-precommit-linter and the current args list to locate where to
change).